<!DOCTYPE html>
<html lang="en-us">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    
<meta charset="UTF-8">
<title>Using Stopwords | Elasticsearch: The Definitive Guide [2.x] | Elastic</title>
<link rel="home" href="index.html" title="Elasticsearch: The Definitive Guide [2.x]">
<link rel="up" href="stopwords.html" title="Stopwords: Performance Versus Precision">
<link rel="prev" href="pros-cons-stopwords.html" title="Pros and Cons of Stopwords">
<link rel="next" href="stopwords-performance.html" title="Stopwords and Performance">
<meta name="DC.type" content="Learn/Docs/Legacy/Elasticsearch/Definitive Guide/2.x">
<meta name="DC.subject" content="Elasticsearch">
<meta name="DC.identifier" content="2.x">
<meta name="robots" content="noindex,nofollow">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <script src="https://cdn.optimizely.com/js/18132920325.js"></script>
    <link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
    <link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
    <link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
    <link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
    <link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
    <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
    <link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
    <link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
    <link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
    <link rel="manifest" href="/manifest.json">
    <meta name="apple-mobile-web-app-title" content="Elastic">
    <meta name="application-name" content="Elastic">
    <meta name="msapplication-TileColor" content="#ffffff">
    <meta name="msapplication-TileImage" content="/mstile-144x144.png">
    <meta name="theme-color" content="#ffffff">
    <meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd">
    <meta name="yandex-verification" content="d8a47e95d0972434">
    <meta name="localized" content="true">
    <meta name="st:robots" content="follow,index">
    <meta property="og:image" content="https://www.elastic.co/static/images/elastic-logo-200.png">
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
    <link rel="icon" href="/favicon.ico" type="image/x-icon">
    <link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
    <link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
    <link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
    <link rel="stylesheet" type="text/css" href="/guide/static/styles.css">
  </head>

  <!--© 2015-2021 Elasticsearch B.V. Copying, publishing and/or distributing without written permission is strictly prohibited.-->

  <body>
    <!-- Google Tag Manager -->
    <script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
    <!-- End Google Tag Manager -->

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
      gtag('config', 'UA-12395217-16');
    </script>

    <!--BEGIN QUALTRICS WEBSITE FEEDBACK SNIPPET-->
    <script type="text/javascript">
      (function(){var g=function(e,h,f,g){
      this.get=function(a){for(var a=a+"=",c=document.cookie.split(";"),b=0,e=c.length;b<e;b++){for(var d=c[b];" "==d.charAt(0);)d=d.substring(1,d.length);if(0==d.indexOf(a))return d.substring(a.length,d.length)}return null};
      this.set=function(a,c){var b="",b=new Date;b.setTime(b.getTime()+6048E5);b="; expires="+b.toGMTString();document.cookie=a+"="+c+b+"; path=/; "};
      this.check=function(){var a=this.get(f);if(a)a=a.split(":");else if(100!=e)"v"==h&&(e=Math.random()>=e/100?0:100),a=[h,e,0],this.set(f,a.join(":"));else return!0;var c=a[1];if(100==c)return!0;switch(a[0]){case "v":return!1;case "r":return c=a[2]%Math.floor(100/c),a[2]++,this.set(f,a.join(":")),!c}return!0};
      this.go=function(){if(this.check()){var a=document.createElement("script");a.type="text/javascript";a.src=g;document.body&&document.body.appendChild(a)}};
      this.start=function(){var a=this;window.addEventListener?window.addEventListener("load",function(){a.go()},!1):window.attachEvent&&window.attachEvent("onload",function(){a.go()})}};
      try{(new g(100,"r","QSI_S_ZN_emkP0oSe9Qrn7kF","https://znemkp0ose9qrn7kf-elastic.siteintercept.qualtrics.com/WRSiteInterceptEngine/?Q_ZID=ZN_emkP0oSe9Qrn7kF")).start()}catch(i){}})();
    </script><div id="ZN_emkP0oSe9Qrn7kF"><!--DO NOT REMOVE-CONTENTS PLACED HERE--></div>
    <!--END WEBSITE FEEDBACK SNIPPET-->

    <div id="elastic-nav" style="display:none;"></div>
    <script src="https://www.elastic.co/elastic-nav.js"></script>

    <!-- Subnav -->
    <div>
      <div>
        <div class="tertiary-nav d-none d-md-block">
          <div class="container">
            <div class="p-t-b-15 d-flex justify-content-between nav-container">
              <div class="breadcrum-wrapper"><span><a href="/guide/" style="font-size: 14px; font-weight: 600; color: #000;">Docs</a></span></div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div class="main-container">
      <section id="content">
        <div class="content-wrapper">

          <section id="guide" lang="en">
            <div class="container">
              <div class="row">
                <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                  <!-- start body -->
                  <div class="page_header">
<p>
  <strong>WARNING</strong>: The 2.x versions of Elasticsearch have passed their
  <a href="https://www.elastic.co/support/eol">EOL dates</a>. If you are running
  a 2.x version, we strongly advise you to upgrade.
</p>
<p>
  This documentation is no longer maintained and may be removed. For the latest
  information, see the <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html">current
  Elasticsearch documentation</a>.
</p>
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch: The Definitive Guide [2.x]</a></span>
»
<span class="breadcrumb-link"><a href="languages.html">Dealing with Human Language</a></span>
»
<span class="breadcrumb-link"><a href="stopwords.html">Stopwords: Performance Versus Precision</a></span>
»
<span class="breadcrumb-node">Using Stopwords</span>
</div>
<div class="navheader">
<span class="prev">
<a href="pros-cons-stopwords.html">« Pros and Cons of Stopwords</a>
</span>
<span class="next">
<a href="stopwords-performance.html">Stopwords and Performance »</a>
</span>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="using-stopwords"></a>Using Stopwords<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h2>
</div></div></div>
<p>The removal of stopwords is handled by the
<a href="/guide/en/elasticsearch/reference/2.4/analysis-stop-tokenfilter.html" class="ulink" target="_top"><code class="literal">stop</code> token filter</a> which can be used
when creating a <code class="literal">custom</code> analyzer (see <a class="xref" href="using-stopwords.html#stop-token-filter" title="Using the stop Token Filter">Using the stop Token Filter</a>).
However, some out-of-the-box analyzers come with the <code class="literal">stop</code> filter pre-integrated:</p>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<a href="/guide/en/elasticsearch/reference/2.4/analysis-lang-analyzer.html" class="ulink" target="_top">Language analyzers</a>
</span>
</dt>
<dd>
Each language analyzer defaults to using the appropriate stopwords list
for that language. For instance, the <code class="literal">english</code> analyzer uses the
<code class="literal">_english_</code> stopwords list.
</dd>
<dt>
<span class="term">
<a href="/guide/en/elasticsearch/reference/2.4/analysis-standard-analyzer.html" class="ulink" target="_top"><code class="literal">standard</code> analyzer</a>
</span>
</dt>
<dd>
Defaults to the empty stopwords list: <code class="literal">_none_</code>, essentially disabling
stopwords.
</dd>
<dt>
<span class="term">
<a href="/guide/en/elasticsearch/reference/2.4/analysis-pattern-analyzer.html" class="ulink" target="_top"><code class="literal">pattern</code> analyzer</a>
</span>
</dt>
<dd>
Defaults to <code class="literal">_none_</code>, like the <code class="literal">standard</code> analyzer.
</dd>
</dl>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_stopwords_and_the_standard_analyzer"></a>Stopwords and the Standard Analyzer<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h3>
</div></div></div>
<p>To use custom stopwords in conjunction with the <code class="literal">standard</code> analyzer, all we
need to do is to create a configured version of the analyzer and pass in the
list of <code class="literal">stopwords</code> that we require:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">PUT /my_index
{
  "settings": {
    "analysis": {
      "analyzer": {
        "my_analyzer": { <a id="CO167-1"></a><i class="conum" data-value="1"></i>
          "type": "standard", <a id="CO167-2"></a><i class="conum" data-value="2"></i>
          "stopwords": [ "and", "the" ] <a id="CO167-3"></a><i class="conum" data-value="3"></i>
        }
      }
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO167-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>This is a custom analyzer called <code class="literal">my_analyzer</code>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO167-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>This analyzer is the <code class="literal">standard</code> analyzer with some custom configuration.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO167-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>The stopwords to filter out are <code class="literal">and</code> and <code class="literal">the</code>.</p>
</td>
</tr>
</table>
</div>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>This same technique can be used to configure custom stopword lists for
any of the language analyzers.</p>
</div>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="maintaining-positions"></a>Maintaining Positions<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The output from the <code class="literal">analyze</code> API is quite interesting:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">GET /my_index/_analyze?analyzer=my_analyzer
The quick and the dead</pre>
</div>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">{
   "tokens": [
      {
         "token":        "quick",
         "start_offset": 4,
         "end_offset":   9,
         "type":         "&lt;ALPHANUM&gt;",
         "position":     1 <a id="CO168-1"></a><i class="conum" data-value="1"></i>
      },
      {
         "token":        "dead",
         "start_offset": 18,
         "end_offset":   22,
         "type":         "&lt;ALPHANUM&gt;",
         "position":     4 <a id="CO168-2"></a><i class="conum" data-value="1"></i>
      }
   ]
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO168-1"><i class="conum" data-value="1"></i></a><a href="#CO168-2"></a></p>
</td>
<td align="left" valign="top">
<p>Note the <code class="literal">position</code> of each token.</p>
</td>
</tr>
</table>
</div>
<p>The stopwords have been filtered out, as expected, but the interesting part is
that the <code class="literal">position</code> of the two remaining terms is unchanged: <code class="literal">quick</code> is the
second word in the original sentence, and <code class="literal">dead</code> is the fifth. This is
important for phrase queries—​if the positions of each term had been
adjusted, a phrase query for <code class="literal">quick dead</code> would have matched the preceding
example incorrectly.</p>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="specifying-stopwords"></a>Specifying Stopwords<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Stopwords can be passed inline, as we did in the previous example, by
specifying an array:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">"stopwords": [ "and", "the" ]</pre>
</div>
<p>The default stopword list for a particular language can be specified using the
<code class="literal">_lang_</code> notation:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">"stopwords": "_english_"</pre>
</div>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>The predefined language-specific stopword lists available in
Elasticsearch can be found in the
<a href="/guide/en/elasticsearch/reference/2.4/analysis-stop-tokenfilter.html" class="ulink" target="_top"><code class="literal">stop</code> token filter</a> documentation.</p>
</div>
</div>
<p>Stopwords can be disabled by specifying the special list: <code class="literal">_none_</code>.  For
instance, to use the <code class="literal">english</code> analyzer without stopwords, you can do the
following:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">PUT /my_index
{
  "settings": {
    "analysis": {
      "analyzer": {
        "my_english": {
          "type":      "english", <a id="CO169-1"></a><i class="conum" data-value="1"></i>
          "stopwords": "_none_" <a id="CO169-2"></a><i class="conum" data-value="2"></i>
        }
      }
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO169-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">my_english</code> analyzer is based on the <code class="literal">english</code> analyzer.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO169-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>But stopwords are disabled.</p>
</td>
</tr>
</table>
</div>
<p>Finally, stopwords can also be listed in a file with one word per line.  The
file must be present on all nodes in the cluster, and the path can be
specified with the <code class="literal">stopwords_path</code> parameter:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">PUT /my_index
{
  "settings": {
    "analysis": {
      "analyzer": {
        "my_english": {
          "type":           "english",
          "stopwords_path": "stopwords/english.txt" <a id="CO170-1"></a><i class="conum" data-value="1"></i>
        }
      }
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO170-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The path to the stopwords file, relative to the Elasticsearch <code class="literal">config</code>
directory</p>
</td>
</tr>
</table>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="stop-token-filter"></a>Using the stop Token Filter<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The <a href="/guide/en/elasticsearch/reference/2.4/analysis-stop-tokenfilter.html" class="ulink" target="_top"><code class="literal">stop</code> token filter</a> can be combined
with a tokenizer and other token filters when you need to create a <code class="literal">custom</code>
analyzer.  For instance, let’s say that we wanted to create a Spanish analyzer
with the following:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
A custom stopwords list
</li>
<li class="listitem">
The <code class="literal">light_spanish</code> stemmer
</li>
<li class="listitem">
The <a class="xref" href="asciifolding-token-filter.html" title="You Have an Accent"><code class="literal">asciifolding</code> filter</a> to remove diacritics
</li>
</ul>
</div>
<p>We could set that up as follows:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">PUT /my_index
{
  "settings": {
    "analysis": {
      "filter": {
        "spanish_stop": {
          "type":        "stop",
          "stopwords": [ "si", "esta", "el", "la" ]  <a id="CO171-1"></a><i class="conum" data-value="1"></i>
        },
        "light_spanish": { <a id="CO171-2"></a><i class="conum" data-value="2"></i>
          "type":     "stemmer",
          "language": "light_spanish"
        }
      },
      "analyzer": {
        "my_spanish": {
          "tokenizer": "spanish",
          "filter": [ <a id="CO171-3"></a><i class="conum" data-value="3"></i>
            "lowercase",
            "asciifolding",
            "spanish_stop",
            "light_spanish"
          ]
        }
      }
    }
  }
}</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO171-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">stop</code> token filter takes the same <code class="literal">stopwords</code> and <code class="literal">stopwords_path</code>
parameters as the <code class="literal">standard</code> analyzer.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO171-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>See <a class="xref" href="algorithmic-stemmers.html" title="Algorithmic Stemmers">Algorithmic Stemmers</a>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO171-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>The order of token filters is important, as explained next.</p>
</td>
</tr>
</table>
</div>
<p>We have placed the <code class="literal">spanish_stop</code> filter after the <code class="literal">asciifolding</code> filter. This
means that <code class="literal">esta</code>, <code class="literal">ésta</code>, and <code class="literal">está</code> will first have their diacritics
removed to become just <code class="literal">esta</code>, which will then be removed as a stopword. If,
instead, we wanted to remove <code class="literal">esta</code> and <code class="literal">ésta</code>, but not <code class="literal">está</code>, we
would have to put the <code class="literal">spanish_stop</code> filter <em>before</em> the <code class="literal">asciifolding</code>
filter, and specify both words in the stopwords list.</p>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="updating-stopwords"></a>Updating Stopwords<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch-definitive-guide/edit/2.x/240_Stopwords/20_Using_stopwords.asciidoc">edit</a>
</h3>
</div></div></div>
<p>A few techniques can be used to update the list of stopwords
used by an analyzer. Analyzers are instantiated at index creation time, when a
node is restarted, or when a closed index is reopened.</p>
<p>If you specify stopwords inline with the <code class="literal">stopwords</code> parameter, your
only option is to close the index and update the analyzer configuration with the
<a href="/guide/en/elasticsearch/reference/2.4/indices-update-settings.html#update-settings-analysis" class="ulink" target="_top">update index settings API</a>, then reopen
the index.</p>
<p>Updating stopwords is easier if you specify them in a file with the
<code class="literal">stopwords_path</code> parameter.  You can just update the file (on every node in
the cluster) and then force the analyzers to be re-created by either of these actions:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Closing and reopening the index
(see <a href="/guide/en/elasticsearch/reference/2.4/indices-open-close.html" class="ulink" target="_top">open/close index</a>), or
</li>
<li class="listitem">
Restarting each node in the cluster, one by one
</li>
</ul>
</div>
<p>Of course, updating the stopwords list will not change any documents that have
already been indexed. It will apply only to searches and to new or updated
documents.  To apply the changes to existing documents, you will need to
reindex your data. See <a class="xref" href="reindex.html" title="Reindexing Your Data">Reindexing Your Data</a>.</p>
</div>

</div>
<div class="navfooter">
<span class="prev">
<a href="pros-cons-stopwords.html">« Pros and Cons of Stopwords</a>
</span>
<span class="next">
<a href="stopwords-performance.html">Stopwords and Performance »</a>
</span>
</div>
</div>

                  <!-- end body -->
                </div>
                <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                  <div id="rtpcontainer" style="display: block;">
                    <div class="mktg-promo">
                      <h3>Most Popular</h3>
                      <ul class="icons">
                        <li class="icon-elasticsearch-white"><a href="https://www.elastic.co/webinars/getting-started-elasticsearch?baymax=default&amp;elektra=docs&amp;storm=top-video">Get Started with Elasticsearch: Video</a></li>
                        <li class="icon-kibana-white"><a href="https://www.elastic.co/webinars/getting-started-kibana?baymax=default&amp;elektra=docs&amp;storm=top-video">Intro to Kibana: Video</a></li>
                        <li class="icon-logstash-white"><a href="https://www.elastic.co/webinars/introduction-elk-stack?baymax=default&amp;elektra=docs&amp;storm=top-video">ELK for Logs &amp; Metrics: Video</a></li>
                      </ul>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </section>

        </div>


<div id="elastic-footer"></div>
<script src="https://www.elastic.co/elastic-footer.js"></script>
<!-- Footer Section end-->

      </section>
    </div>

<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
  window.initial_state = {}</script>
  </body>
</html>
